Build Type 1 binding features #567
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR extends the basic infrastructure added in previous PRs (#553, #554, #557, #560, runtimeverification/k#2873) to build the actual features required of the Type 1 (no definition) Python bindings.
The features added are sufficient to construct (programmatically and via the KORE parser) and manipulate KORE pattern ASTs. It doesn't yet expose the full generality of the Module / Definition structure, or the KORE binary serializer. The Type 2 (i.e. runtime) features will be added separately.
It also extends the existing test infrastructure to add Python tests that load the compiled bindings from the current build; these tests should give a rough idea of how to use the Python bindings from Pyk (for example)
Fixes #565